Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebGPUPipelines: Improve reuse pipeline and ComputeNode dispose #26361

Merged
merged 5 commits into from
Jul 10, 2023

Conversation

sunag
Copy link
Collaborator

@sunag sunag commented Jul 2, 2023

Description

Same thing that #26305 with pipelines.

@sunag sunag added this to the r155 milestone Jul 2, 2023
@sunag sunag marked this pull request as ready for review July 4, 2023 01:15
@LeviPesin
Copy link
Contributor

Why do we need ComputeNode.needsUpdate?

@danrossi
Copy link

danrossi commented Jul 4, 2023

Is it required to change/update pipelines during a loop ? It seems adding these during a loop chews cpu. Thanks for looking into it.

@sunag
Copy link
Collaborator Author

sunag commented Jul 4, 2023

Why do we need ComputeNode.needsUpdate?

To update the compute program if some node is changed, we should also add dispose().

@sunag
Copy link
Collaborator Author

sunag commented Jul 4, 2023

Thanks, @danrossi, I think it will work now. We will just do some additional testing.

@sunag sunag changed the title WebGPUPipelines: Improve reuse pipeline. WebGPUPipelines: Improve reuse pipeline, add ComputeNode .dispose() Jul 9, 2023
@sunag sunag changed the title WebGPUPipelines: Improve reuse pipeline, add ComputeNode .dispose() WebGPUPipelines: Improve reuse pipeline and ComputeNode dispose Jul 9, 2023
@sunag sunag merged commit 1a4f54b into mrdoob:dev Jul 10, 2023
@sunag sunag deleted the dev-reuse-pipeline branch July 10, 2023 04:39
@Methuselah96 Methuselah96 mentioned this pull request Jan 18, 2024
45 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants